@azure-tools/azure-http-specs - internal ✏️

Remove use of implicit optionality which was a noop in one operation

@azure-tools/typespec-azure-resource-manager - breaking ✏️

Removed implicitOptionality: true from the @patch decorator on the following operation templates:,> ,> - ArmTagsPatchAsync,> - ArmResourcePatchAsync,> - ArmTagsPatchSync,> - ArmResourcePatchSync,> - ResourceUpdateSync.update (in ResourceUpdateSync interface),> ,> Previously, these templates used @patch(#{ implicitOptionality: true }) which caused all properties in the PATCH request body to be implicitly treated as optional, regardless of how they were declared in the model. This behavior is now removed — properties will retain their declared optionality.,> ,> #### Migration,> ,> If you use these ARM operation templates, the PATCH body will no longer implicitly make all properties optional. In most cases, ARM resources already use ResourceUpdateModel<Resource, Properties> which produces the correct optional property envelope — if so, no changes are needed.,> ,> If you have a custom patch body that relied on implicit optionality, explicitly mark properties as optional:,> ,> Before (implicit optionality made all properties optional automatically):,> ,> tsp,> model MyResourceProperties {,> displayName: string;,> config: MyConfig;,> },> ,> ,> After (explicitly declare optional properties for update):,> ,> tsp,> model MyResourceUpdateProperties {,> displayName?: string;,> config?: MyConfig;,> },> ,> ,> Or continue using ResourceUpdateModel<Resource, Properties> which already handles this transformation for standard ARM resource patterns.

@azure-tools/typespec-azure-core - breaking ✏️

Removed implicitOptionality: true from the @patch decorator on the following operation templates:,> ,> - ResourceCreateOrUpdate,> - LongRunningResourceCreateOrUpdate,> - ResourceUpdate,> ,> Previously, these templates used @patch(#{ implicitOptionality: true }) which caused all properties in the PATCH request body to be implicitly treated as optional, regardless of how they were declared in the model. This behavior is now removed — properties will retain their declared optionality.,> ,> #### Migration,> ,> If your service relies on all properties being optional in the PATCH body, you need to explicitly mark them as optional in your model:,> ,> Before (implicit optionality made all properties optional automatically):,> ,> tsp,> model Widget {,> name: string;,> color: string;,> },> ,> ,> After (explicitly declare optional properties):,> ,> tsp,> model WidgetUpdate {,> name?: string;,> color?: string;,> },> ,> ,> Alternatively, you can use the ResourceUpdateModel template or OptionalProperties utility to derive an all-optional version of your model for PATCH operations. If you were already using ResourceUpdateModel<Resource> or manually defining optional properties in your update model, no changes are needed.

Averaged across 3 specs (azure-arm-resource-manager, azure-core-dataplane, azure-full).
Threshold: changes > ±5% are highlighted.
🟢 Fast · 🟡 Moderate (stages >200ms, rules >10ms) · 🔴 Slow (stages >400ms, rules >20ms)